← Home

@tmlmobilidade/rss

npm Repository Homepage
26
Versions
AGPL-3.0-or-later
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

joaovasconcelosjusimen

Keywords

public transittmltransportes metropolitanos de lisboago

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Org consistently publishes without provenance attestation; stable pattern. ai
publish-pattern rapid-publish AI (publish-pattern): High-frequency automated CI releases are the norm for this org's versioning scheme (date-based versions, 128 registry versions). ai
npm-metadata no-description AI (npm-metadata): Org-internal package; missing description is a stable pattern across this publisher's packages. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped org package @tmlmobilidade/rss; 'rss' is a legitimate module name, not a typosquat of 'qs'. ai
typosquat typosquat.levenshtein:rxjs AI (typosquat): Scoped org package @tmlmobilidade/rss; 'rss' is a legitimate module name, not a typosquat of 'rxjs'. ai
phantom-deps phantom-dep:@tmlmobilidade/dates AI (phantom-deps): Same org scope; likely used transitively or in type-only capacity within the monorepo. ai

Versions (showing 26 of 26)

Version Deps Published
20260602.2322.45 1 / 6
20260601.1620.24 1 / 6
20260528.1805.36 1 / 6
20260528.1745.17 1 / 6
20260525.1751.19 1 / 6
20260525.1717.19 1 / 6
20260525.1615.59 1 / 6
20260525.1614.32 1 / 6
20260519.1152.59 1 / 6
20260518.901.35 1 / 6
20260518.827.12 1 / 6
20260517.2113.47 1 / 6
20260516.1537.21 1 / 6
20260515.1056.47 1 / 6
20260507.1753.34 1 / 6
20260507.11.20 1 / 6
20260505.2344.52 1 / 6
20260505.2251.5 1 / 6
20260504.1404.42 1 / 6
20260504.1217.59 1 / 6
20260504.1217.50 1 / 6
20260504.1211.57 1 / 6
20260429.1713.40 1 / 6
20260424.1352.48 1 / 6
20260423.1140.30 1 / 6
20260406.1442.3 1 / 6

v20260602.2322.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260601.1620.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260528.1805.36

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jusimen → joaovasconcelos (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (joaovasconcelos) than the most recent previously approved version (jusimen) on 2026-05-28, but joaovasconcelos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v20260528.1745.17

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jusimen → joaovasconcelos (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (joaovasconcelos) than the most recent previously approved version (jusimen) on 2026-05-28, but joaovasconcelos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v20260525.1751.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1717.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1615.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1614.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260519.1152.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.901.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.827.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260517.2113.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260516.1537.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260515.1056.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260507.1753.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260507.11.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260505.2344.52

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260505.2251.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1404.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1217.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1217.50

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1211.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260429.1713.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260424.1352.48

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260423.1140.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260406.1442.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.